web/src/pages/stats/index.tsx (3)

1022-1022: 多余的 JSX 空白字符字面量

</ComposedChart>{' '} 中的 {' '} 是无意义的空格字面量，建议删除。

🧹 建议修复

-                      </ComposedChart>{' '}
+                      </ComposedChart>

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@web/src/pages/stats/index.tsx` at line 1022, Remove the meaningless
whitespace literal after the ComposedChart closing tag: locate the closing JSX
tag </ComposedChart> in the stats page component and delete the trailing {' '}
token so the JSX no longer contains the redundant space literal; no other logic
changes are needed (keep the rest of the surrounding JSX as-is).

---

729-739: 统计页的项目筛选列表未同步排序

projects/index.tsx 已按 createdAt 升序排序（修复 issue #204），但此处的项目筛选 chips 仍直接遍历原始 projects（API 返回顺序），导致两处展示顺序不一致。

♻️ 建议在筛选列表中应用相同排序

-{projects && projects.length > 0 && (
+{projects && projects.length > 0 && (() => {
+  const sorted = projects.slice().sort((a, b) => {
+    const tA = new Date(a.createdAt).getTime() || 0;
+    const tB = new Date(b.createdAt).getTime() || 0;
+    return tA !== tB ? tA - tB : a.id - b.id;
+  });
+  return (
   <FilterSection
     label={t('stats.project')}
     showClear={projectId !== 'all'}
     onClear={() => setProjectId('all')}
   >
-    {projects.map((p) => (
+    {sorted.map((p) => (
       <FilterChip
         key={p.id}
         selected={projectId === String(p.id)}
         onClick={() => setProjectId(String(p.id))}
       >
         {p.name}
       </FilterChip>
     ))}
   </FilterSection>
-)}
+  );
+})()}

或者将排序逻辑提取为与 projects/index.tsx 共享的 hook/util。

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@web/src/pages/stats/index.tsx` around lines 729 - 739, The project filter
chips are rendered from the unsorted projects array (projects.map) causing order
mismatch with projects/index.tsx which sorts by createdAt; update the rendering
in the stats page to use the same sort (e.g., sort projects by createdAt
ascending before mapping to FilterChip, or move the sorting into a shared
utility/hook used by both pages) so FilterChip, projectId and setProjectId usage
remains identical but the list order matches projects/index.tsx.

---

481-481: keepPreviousData 下切换筛选条件无加载反馈

启用 keepPreviousData 后，切换筛选条件时 isLoading 保持 false（占位数据存在），图表会静默显示旧数据直到新数据到达，用户无法感知正在刷新。

♻️ 建议利用 `isFetching` 展示轻量加载状态

-const { data: stats, isLoading } = useUsageStats(filter);
+const { data: stats, isLoading, isFetching, isPlaceholderData } = useUsageStats(filter);

然后在图表卡片上叠加半透明遮罩或微型 spinner：

-<Card className="border-border/50 bg-card/50 backdrop-blur-sm">
+<Card className={cn('border-border/50 bg-card/50 backdrop-blur-sm', isFetching && 'opacity-60 pointer-events-none')}>

Also applies to: 882-885

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@web/src/pages/stats/index.tsx` at line 481, The current use of
useUsageStats(filter) with keepPreviousData causes isLoading to stay false
during filter switches, so add useUsageStats's isFetching (e.g., const { data:
stats, isLoading, isFetching } = useUsageStats(filter)) and use isFetching to
drive a lightweight loading UI; update the chart/card components that render
stats to show a semi-transparent overlay or small spinner when isFetching is
true (while still rendering previous stats) so users see a refresh indicator —
adjust the chart container(s) where stats is used to conditionally render the
overlay based on isFetching.

web/src/pages/projects/index.tsx (1)

48-59: 排序比较器中每项 Date 对象重复实例化

new Date(a.createdAt) 在 Number.isFinite(...) 检查和 .getTime() 取值时各创建一次，可合并为一次。

♻️ 建议优化

 return projects.slice().sort((a, b) => {
-  const timeA = Number.isFinite(new Date(a.createdAt).getTime())
-    ? new Date(a.createdAt).getTime()
-    : 0;
-  const timeB = Number.isFinite(new Date(b.createdAt).getTime())
-    ? new Date(b.createdAt).getTime()
-    : 0;
+  const rawA = new Date(a.createdAt).getTime();
+  const rawB = new Date(b.createdAt).getTime();
+  const timeA = Number.isFinite(rawA) ? rawA : 0;
+  const timeB = Number.isFinite(rawB) ? rawB : 0;
   if (timeA !== timeB) {
     return timeA - timeB;
   }
   return a.id - b.id;
 });

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@web/src/pages/projects/index.tsx` around lines 48 - 59, The sort comparator
repeatedly constructs Date objects for each side (new Date(a.createdAt) and new
Date(b.createdAt)) twice; to fix, create and reuse a single Date instance per
item inside the comparator (e.g., const dateA = new Date(a.createdAt) and const
dateB = new Date(b.createdAt)), compute their getTime() once, validate with
Number.isFinite and fall back to 0, then compare those cached times and finally
a.id - b.id; update the comparator in the projects.slice().sort(...) callback to
use these local dateA/dateB and timeA/timeB variables.

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro